Mobile@Work features

The Mobile@Work features topic describes the supported features and other information about the Mobile@Work for iOS and the Mobile@Work for Android clients after migrating the respective devices from EPMM to Ivanti Neurons for MDM.

Starting from release 12, irrespective of whether the Mobile@Work client that is registered on the device supports migration the device can be migrated. For devices that have unsupported Client versions and are migrated to Ivanti Neurons for MDM, the device will be marked as Client Unmigratable in the Migration Portal to indicate the unsuccessful migration to the administrator. The administrator can mark the Client Unmigratable devices as Resolved.

Mobile@Work common features

  • The Forgot Password functionality will work only for new devices migrated after Migration Portal R6 release.

  • The user custom attributes will be pushed to Ivanti Neurons for MDM only for new devices migrated after Migration Portal R6 release. The user custom attributes should be re-created in Ivanti Neurons for MDM (via ETL) before triggering migration, otherwise the migration will fail.

Mobile@Work for iOS features

  • Before migrating a device, users must upgrade to Mobile@Work for iOS 12.1.0 (or later versions) for the Forgot Passcode and Reset Passcode features to work. If the Mobile@Work for iOS client is upgraded after the device migration, the features will not work.
  • When a device running Mobile@Work for iOS is migrated from EPMM to Ivanti Neurons for MDM, the Privacy tab in the Settings menu will be no longer available in Mobile@Work.
  • During the migration of a device from EPMM to Ivanti Neurons for MDM, if there are any errors, then Mobile@Work will notify the user that the migration failed and will provide the following options:
    • Send Mobile@Work for iOS Logs - Contact Ivanti Neurons for MDM Support with the logs for troubleshooting any issues.
    • Exit - Close the client and relaunch Mobile@Work for iOS.
  • Post-migration of a device, if the administrator retires the device, Mobile@Work for iOS notifies the user that they cannot use this client because it was retired. The user is prompted with the following option:
    • Install Go App - Go to the App Store to install the Go for iOS app.
  • Post-migration of a device, the re-enroll option is not supported in Mobile@Work for iOS.
  • Post-migration of a device, if the device is registered with a local user, the local user must reset their passcode. The administrator can either send an email to user or set the passcode directly in the Ivanti Neurons for MDM administrator portal.
  • Post-migration of a device, Mobile@Work for iOS allows AppConnect app authorization to communicate with Ivanti Neurons for MDM. Derived credentials are not supported.
  • Post-migration of a device, if the AppConnect Policy was configured on EPMM, the passcode is prompted on launching the Mobile@Work for iOS client.

  • During the migration of a device, only the configurations are cleared from the system, not the policies. If Ivanti Neurons for MDM fails to send any new or updated policies, then the older policies from EPMM are enforced on the migrated devices.

  • A new key-value pair migrate_from_email_exchange_host is required to configure the migration of email accounts, and the value should be the previous email_exchange_host key that was set up on EPMM.

  • The Email+ inbox re-sync can be avoided only for new devices migrated after Migration Portal R6 release.

Mobile@Work for Android features

  • Mobile@Work for Android handles the following device registration settings during the migration of Android devices. Mobile@Work for Android attempts the migration thrice before it reports an error code and a message on the Migration Portal and then displays the error message to the users. During a subsequent check-in, if a migration request is placed, Mobile@Work for Android initiates the migration again.

    • Enable Minimum Version

    • Minimum Security Patch Level

    • Manufacturer Whitelist/Blacklist

    • Minimum SafetyNet Certification

  • If there are any errors during the migration of a device from EPMM to Ivanti Neurons for MDM, Mobile@Work for Android notifies the user with a message.
  • If there are any errors during migration, the errors are reported to the Migration Portal.
  • If an administrator retires a device that has Mobile@Work for Android and migrates the device from EPMM to Ivanti Neurons for MDM, Mobile@Work for Android notifies the user that they cannot use the client as the device is retired. The user must uninstall Mobile@Work for Android and install the Go for Android application from the Google Play store. The user is prompted with the following options:
    • Send Logs - Contact Ivanti Neurons for MDM Support with the logs for troubleshooting any issues.
    • Exit - Close the app.

  • Some devices display a red logo instead of a blue one. You can ignore this indication.

  • The key-value pair migrate_from_email_exchange_host is required to configure the migration of email accounts, and the value should be the previous email_exchange_host key that was set up on EPMM.

  • For Android Enterprise devices, post-migration of a device, the Email+ app will need to be re-synced to continue receiving and sending email messages. The content in local folders, such as Draft and Outbox, will be removed and no longer available. The inbox should be refreshed for the email list to display.

    If EPMM distributes a firmware policy to a device before the device migrates to Ivanti Neurons for MDM, the policy does not get uninstalled even if Ivanti Neurons for MDM does not distribute the same policy.

    • WebApps are not similar to private apps, as web apps are not available in Google Play and cannot be associated to more than one Android enterprise ID at a time. The same WebApp is not available to the Ivanti Neurons for MDM enterprise and EPMM enterprise.If we create a WebApps on the Ivanti Neurons for MDM UI it will be installed on the Ivanti Neurons for MDM native devices but not on migrated devices. It is not possible to install Ivanti Neurons for MDM native WebApps on migrated devices even though we have same WebApps on EPMM and Ivanti Neurons for MDM, this is a known limitation.

Related Topics